Pre-positioning pre-stored content in a content distribution system

ABSTRACT

A method for execution by one or more processing modules of one or more computing devices of a dispersed storage network (DSN), the method begins by selecting a plurality of network edge units for staging public pillar encoded data slices. The method continues by identifying target content for partial download to the plurality of network edge units. The method continues by identifying public pillars corresponding to the target content for partial download. The method continues by determining a partial downloading schedule for sending public pillar encoded data slices, corresponding to the public pillars, to each network edge unit of the plurality of network edge units and facilitating partial downloading of the target content by facilitating sending of the public pillar encoded data slices to each network edge unit of the plurality of network edge units.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present U.S. Utility Patent Application claims priority pursuant to 35 U.S.C. § 120 as a continuation-in-part of U.S. Utility application Ser. No. 15/190,925, entitled “WIRELESSLY COMMUNICATING A DATA FILE”, filed Jun. 23, 2016, which is a continuation of U.S. Utility application Ser. No. 13/647,528, entitled “WIRELESSLY COMMUNICATING A DATA FILE”, filed Oct. 9, 2012, now U.S. Pat. No. 9,400,714, which is a continuation-in-part of U.S. Utility patent application Ser. No. 13/464,166, entitled “DISTRIBUTING MULTI-MEDIA CONTENT TO A PLURALITY OF POTENTIAL ACCESSING DEVICES,” filed May 4, 2012, now U.S. Pat. No. 8,762,479, which claims priority pursuant to 35 U.S.C. § 119(e) to U.S. Provisional Application No. 61/493,825, entitled “ACCESSING DATA IN A DISPERSED STORAGE NETWORK,” filed Jun. 6, 2011.

U.S. Utility patent application Ser. No. 13/647,528 also claims priority pursuant to 35 U.S.C. § 119(e) to U.S. Provisional Application No. 61/554,152, entitled “COMMUNICATING DATA UTILIZING DATA DISPERSAL,” filed Nov. 1, 2011, which is incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not applicable.

BACKGROUND OF THE INVENTION Technical Field of the Invention

This invention relates generally to computer networks and more particularly to dispersing error encoded data.

Description of Related Art

Computing devices are known to communicate data, process data, and/or store data. Such computing devices range from wireless smart phones, laptops, tablets, personal computers (PC), work stations, and video game devices, to data centers that support millions of web searches, stock trades, or on-line purchases every day. In general, a computing device includes a central processing unit (CPU), a memory system, user input/output interfaces, peripheral device interfaces, and an interconnecting bus structure.

As is further known, a computer may effectively extend its CPU by using “cloud computing” to perform one or more computing functions (e.g., a service, an application, an algorithm, an arithmetic logic function, etc.) on behalf of the computer. Further, for large services, applications, and/or functions, cloud computing may be performed by multiple cloud computing resources in a distributed manner to improve the response time for completion of the service, application, and/or function. For example, Hadoop is an open source software framework that supports distributed applications enabling application execution by thousands of computers.

In addition to cloud computing, a computer may use “cloud storage” as part of its memory system. As is known, cloud storage enables a user, via its computer, to store files, applications, etc. on an Internet storage system. The Internet storage system may include a RAID (redundant array of independent disks) system and/or a dispersed storage system that uses an error correction scheme to encode data for storage.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a dispersed or distributed storage network (DSN) in accordance with the present invention;

FIG. 2 is a schematic block diagram of an embodiment of a computing core in accordance with the present invention;

FIG. 3 is a schematic block diagram of an example of dispersed storage error encoding of data in accordance with the present invention;

FIG. 4 is a schematic block diagram of a generic example of an error encoding function in accordance with the present invention;

FIG. 5 is a schematic block diagram of a specific example of an error encoding function in accordance with the present invention;

FIG. 6 is a schematic block diagram of an example of a slice name of an encoded data slice (EDS) in accordance with the present invention;

FIG. 7 is a schematic block diagram of an example of dispersed storage error decoding of data in accordance with the present invention;

FIG. 8 is a schematic block diagram of a generic example of an error decoding function in accordance with the present invention;

FIG. 9 is a schematic block diagram of another embodiment of a computing system in accordance with the invention;

FIG. 9A is a flowchart illustrating an example of staging content for downloading in accordance with the invention; and

FIG. 9B is a flowchart illustrating an example of staging content for downloading in accordance with the invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of an embodiment of a dispersed, or distributed, storage network (DSN) 10 that includes a plurality of computing devices 12-16, a managing unit 18, an integrity processing unit 20, and a DSN memory 22. The components of the DSN 10 are coupled to a network 24, which may include one or more wireless and/or wire lined communication systems; one or more non-public intranet systems and/or public internet systems; and/or one or more local area networks (LAN) and/or wide area networks (WAN).

The DSN memory 22 includes a plurality of storage units 36 that may be located at geographically different sites (e.g., one in Chicago, one in Milwaukee, etc.), at a common site, or a combination thereof. For example, if the DSN memory 22 includes eight storage units 36, each storage unit is located at a different site. As another example, if the DSN memory 22 includes eight storage units 36, all eight storage units are located at the same site. As yet another example, if the DSN memory 22 includes eight storage units 36, a first pair of storage units are at a first common site, a second pair of storage units are at a second common site, a third pair of storage units are at a third common site, and a fourth pair of storage units are at a fourth common site. Note that a DSN memory 22 may include more or less than eight storage units 36. Further note that each storage unit 36 includes a computing core (as shown in FIG. 2, or components thereof) and a plurality of memory devices for storing dispersed error encoded data.

Each of the computing devices 12-16, the managing unit 18, and the integrity processing unit 20 include a computing core 26, which includes network interfaces 30-33. Computing devices 12-16 may each be a portable computing device and/or a fixed computing device. A portable computing device may be a social networking device, a gaming device, a cell phone, a smart phone, a digital assistant, a digital music player, a digital video player, a laptop computer, a handheld computer, a tablet, a video game controller, and/or any other portable device that includes a computing core. A fixed computing device may be a computer (PC), a computer server, a cable set-top box, a satellite receiver, a television set, a printer, a fax machine, home entertainment equipment, a video game console, and/or any type of home or office computing equipment. Note that each of the managing unit 18 and the integrity processing unit 20 may be separate computing devices, may be a common computing device, and/or may be integrated into one or more of the computing devices 12-16 and/or into one or more of the storage units 36.

Each interface 30, 32, and 33 includes software and hardware to support one or more communication links via the network 24 indirectly and/or directly. For example, interface 30 supports a communication link (e.g., wired, wireless, direct, via a LAN, via the network 24, etc.) between computing devices 14 and 16. As another example, interface 32 supports communication links (e.g., a wired connection, a wireless connection, a LAN connection, and/or any other type of connection to/from the network 24) between computing devices 12 & 16 and the DSN memory 22. As yet another example, interface 33 supports a communication link for each of the managing unit 18 and the integrity processing unit 20 to the network 24.

Computing devices 12 and 16 include a dispersed storage (DS) client module 34, which enables the computing device to dispersed storage error encode and decode data as subsequently described with reference to one or more of FIGS. 3-9B. In this example embodiment, computing device 16 functions as a dispersed storage processing agent for computing device 14. In this role, computing device 16 dispersed storage error encodes and decodes data on behalf of computing device 14. With the use of dispersed storage error encoding and decoding, the DSN 10 is tolerant of a significant number of storage unit failures (the number of failures is based on parameters of the dispersed storage error encoding function) without loss of data and without the need for a redundant or backup copies of the data. Further, the DSN 10 stores data for an indefinite period of time without data loss and in a secure manner (e.g., the system is very resistant to unauthorized attempts at accessing the data).

In operation, the managing unit 18 performs DS management services. For example, the managing unit 18 establishes distributed data storage parameters (e.g., vault creation, distributed storage parameters, security parameters, billing information, user profile information, etc.) for computing devices 12-14 individually or as part of a group of user devices. As a specific example, the managing unit 18 coordinates creation of a vault (e.g., a virtual memory block associated with a portion of an overall namespace of the DSN) within the DSTN memory 22 for a user device, a group of devices, or for public access and establishes per vault dispersed storage (DS) error encoding parameters for a vault. The managing unit 18 facilitates storage of DS error encoding parameters for each vault by updating registry information of the DSN 10, where the registry information may be stored in the DSN memory 22, a computing device 12-16, the managing unit 18, and/or the integrity processing unit 20.

The DSN managing unit 18 creates and stores user profile information (e.g., an access control list (ACL)) in local memory and/or within memory of the DSN memory 22. The user profile information includes authentication information, permissions, and/or the security parameters. The security parameters may include encryption/decryption scheme, one or more encryption keys, key generation scheme, and/or data encoding/decoding scheme.

The DSN managing unit 18 creates billing information for a particular user, a user group, a vault access, public vault access, etc. For instance, the DSTN managing unit 18 tracks the number of times a user accesses a non-public vault and/or public vaults, which can be used to generate per-access billing information. In another instance, the DSTN managing unit 18 tracks the amount of data stored and/or retrieved by a user device and/or a user group, which can be used to generate per-data-amount billing information.

As another example, the managing unit 18 performs network operations, network administration, and/or network maintenance. Network operations includes authenticating user data allocation requests (e.g., read and/or write requests), managing creation of vaults, establishing authentication credentials for user devices, adding/deleting components (e.g., user devices, storage units, and/or computing devices with a DS client module 34) to/from the DSN 10, and/or establishing authentication credentials for the storage units 36. Network administration includes monitoring devices and/or units for failures, maintaining vault information, determining device and/or unit activation status, determining device and/or unit loading, and/or determining any other system level operation that affects the performance level of the DSN 10. Network maintenance includes facilitating replacing, upgrading, repairing, and/or expanding a device and/or unit of the DSN 10.

The integrity processing unit 20 performs rebuilding of ‘bad’ or missing encoded data slices. At a high level, the integrity processing unit 20 performs rebuilding by periodically attempting to retrieve/list encoded data slices, and/or slice names of the encoded data slices, from the DSN memory 22. For retrieved encoded slices, they are checked for errors due to data corruption, outdated version, etc. If a slice includes an error, it is flagged as a ‘bad’ slice. For encoded data slices that were not received and/or not listed, they are flagged as missing slices. Bad and/or missing slices are subsequently rebuilt using other retrieved encoded data slices that are deemed to be good slices to produce rebuilt slices. The rebuilt slices are stored in the DSTN memory 22.

FIG. 2 is a schematic block diagram of an embodiment of a computing core 26 that includes a processing module 50, a memory controller 52, main memory 54, a video graphics processing unit 55, an input/output (10) controller 56, a peripheral component interconnect (PCI) interface 58, an 10 interface module 60, at least one 10 device interface module 62, a read only memory (ROM) basic input output system (BIOS) 64, and one or more memory interface modules. The one or more memory interface module(s) includes one or more of a universal serial bus (USB) interface module 66, a host bus adapter (HBA) interface module 68, a network interface module 70, a flash interface module 72, a hard drive interface module 74, and a DSN interface module 76.

The DSN interface module 76 functions to mimic a conventional operating system (OS) file system interface (e.g., network file system (NFS), flash file system (FFS), disk file system (DFS), file transfer protocol (FTP), web-based distributed authoring and versioning (WebDAV), etc.) and/or a block memory interface (e.g., small computer system interface (SCSI), internet small computer system interface (iSCSI), etc.). The DSN interface module 76 and/or the network interface module 70 may function as one or more of the interface 30-33 of FIG. 1. Note that the IO device interface module 62 and/or the memory interface modules 66-76 may be collectively or individually referred to as IO ports.

FIG. 3 is a schematic block diagram of an example of dispersed storage error encoding of data. When a computing device 12 or 16 has data to store it disperse storage error encodes the data in accordance with a dispersed storage error encoding process based on dispersed storage error encoding parameters. The dispersed storage error encoding parameters include an encoding function (e.g., information dispersal algorithm, Reed-Solomon, Cauchy Reed-Solomon, systematic encoding, non-systematic encoding, on-line codes, etc.), a data segmenting protocol (e.g., data segment size, fixed, variable, etc.), and per data segment encoding values. The per data segment encoding values include a total, or pillar width, number (T) of encoded data slices per encoding of a data segment i.e., in a set of encoded data slices); a decode threshold number (D) of encoded data slices of a set of encoded data slices that are needed to recover the data segment; a read threshold number (R) of encoded data slices to indicate a number of encoded data slices per set to be read from storage for decoding of the data segment; and/or a write threshold number (W) to indicate a number of encoded data slices per set that must be accurately stored before the encoded data segment is deemed to have been properly stored. The dispersed storage error encoding parameters may further include slicing information (e.g., the number of encoded data slices that will be created for each data segment) and/or slice security information (e.g., per encoded data slice encryption, compression, integrity checksum, etc.).

In the present example, Cauchy Reed-Solomon has been selected as the encoding function (a generic example is shown in FIG. 4 and a specific example is shown in FIG. 5); the data segmenting protocol is to divide the data object into fixed sized data segments; and the per data segment encoding values include: a pillar width of 5, a decode threshold of 3, a read threshold of 4, and a write threshold of 4. In accordance with the data segmenting protocol, the computing device 12 or 16 divides the data (e.g., a file (e.g., text, video, audio, etc.), a data object, or other data arrangement) into a plurality of fixed sized data segments (e.g., 1 through Y of a fixed size in range of Kilo-bytes to Tera-bytes or more). The number of data segments created is dependent of the size of the data and the data segmenting protocol.

The computing device 12 or 16 then disperse storage error encodes a data segment using the selected encoding function (e.g., Cauchy Reed-Solomon) to produce a set of encoded data slices. FIG. 4 illustrates a generic Cauchy Reed-Solomon encoding function, which includes an encoding matrix (EM), a data matrix (DM), and a coded matrix (CM). The size of the encoding matrix (EM) is dependent on the pillar width number (T) and the decode threshold number (D) of selected per data segment encoding values. To produce the data matrix (DM), the data segment is divided into a plurality of data blocks and the data blocks are arranged into D number of rows with Z data blocks per row. Note that Z is a function of the number of data blocks created from the data segment and the decode threshold number (D). The coded matrix is produced by matrix multiplying the data matrix by the encoding matrix.

FIG. 5 illustrates a specific example of Cauchy Reed-Solomon encoding with a pillar number (T) of five and decode threshold number of three. In this example, a first data segment is divided into twelve data blocks (D1-D12). The coded matrix includes five rows of coded data blocks, where the first row of X11-X14 corresponds to a first encoded data slice (EDS 1_1), the second row of X21-X24 corresponds to a second encoded data slice (EDS 2_1), the third row of X31-X34 corresponds to a third encoded data slice (EDS 3_1), the fourth row of X41-X44 corresponds to a fourth encoded data slice (EDS 4_1), and the fifth row of X51-X54 corresponds to a fifth encoded data slice (EDS 5_1). Note that the second number of the EDS designation corresponds to the data segment number.

Returning to the discussion of FIG. 3, the computing device also creates a slice name (SN) for each encoded data slice (EDS) in the set of encoded data slices. A typical format for a slice name 60 is shown in FIG. 6. As shown, the slice name (SN) 60 includes a pillar number of the encoded data slice (e.g., one of 1-T), a data segment number (e.g., one of 1-Y), a vault identifier (ID), a data object identifier (ID), and may further include revision level information of the encoded data slices. The slice name functions as, at least part of, a DSN address for the encoded data slice for storage and retrieval from the DSN memory 22.

As a result of encoding, the computing device 12 or 16 produces a plurality of sets of encoded data slices, which are provided with their respective slice names to the storage units for storage. As shown, the first set of encoded data slices includes EDS 1_1 through EDS 5_1 and the first set of slice names includes SN 1_1 through SN 5_1 and the last set of encoded data slices includes EDS 1_Y through EDS 5_Y and the last set of slice names includes SN 1_Y through SN 5_Y.

FIG. 7 is a schematic block diagram of an example of dispersed storage error decoding of a data object that was dispersed storage error encoded and stored in the example of FIG. 4. In this example, the computing device 12 or 16 retrieves from the storage units at least the decode threshold number of encoded data slices per data segment. As a specific example, the computing device retrieves a read threshold number of encoded data slices.

To recover a data segment from a decode threshold number of encoded data slices, the computing device uses a decoding function as shown in FIG. 8. As shown, the decoding function is essentially an inverse of the encoding function of FIG. 4. The coded matrix includes a decode threshold number of rows (e.g., three in this example) and the decoding matrix in an inversion of the encoding matrix that includes the corresponding rows of the coded matrix. For example, if the coded matrix includes rows 1, 2, and 4, the encoding matrix is reduced to rows 1, 2, and 4, and then inverted to produce the decoding matrix.

FIG. 9 is a schematic block diagram of another embodiment of a computing system. Such a computing system includes a plurality of content providers 1-C, a dispersed storage (DS) processing unit 16, a network 24, a dispersed storage network (DSN) memory 22, a wireless controller 102, a base station 108, a wireless router 104, a distribution server 106, a user device 12, a wireless transceiver 112, a low tier user device 114, and a wireless user device 110. Such a DSN memory 22 includes a plurality of DS units 36. Such a wireless controller, wireless router, distribution server, user device, and a wireless user device may include a slice memory (SM) 116. Such a slice memory includes a temporary slice memory 118 (e.g., for storing encoded data slices on a temporary basis) and a non-temporary slice memory 120 (e.g., for storing encoded data slices on a non-temporary basis).

Such a content provider 1-C may aggregate and store content 122 for distribution to one or more of the user devices (e.g., low tier user device 114, user device 12, wireless user device 110). Such content 122 includes one or more of multimedia, video, movies, music, audio recordings, pictures, sound files, image files, applications, or software. Such content 122 may be associated with a content descriptor including one or more of a content type, a genre type, an artist, a movie type, a music type, a release date, pricing information, purchase indicator information, a demographic indicator, a favorite syndicator, a quality rating, or an industry rating. Such a descriptor may be included with the content 122.

Such a DS processing unit 16 ingests new content 122 by receiving content from the content providers 1-C, dispersed storage error encoding at least some of the content to produce slices 11, and sending slices 11 to the DSN memory 22 for storage in at least some of the DS units 36. Such a DS processing unit 16 distributes content by one or more of receiving a content request and facilitating sending of slices associated with the content of the request to a requesting entity (e.g., a user device 12); and determining target content for a user device, facilitating temporarily storing some slices (e.g., public pillar slices) associated with the target content in the user device 12, and facilitating sending other slices (e.g., private pillar slices) associated with target content to the user device 12 when the user device requests the target content.

A wireless controller 102 controls base station 108 such that the base station converts slices 11 to wide-area signals 124 for transmission to one or more wireless user devices 110. Such a base station 108 may operate in accordance with one or more industry standards (e.g., global system for mobile communications (GSM), code division multiple access (CDMA), etc.) to transmit and receive wide-area signals. A wireless router 104 converts slices 11 into local area signals 126 for transmission to one or more wireless devices. Such a wireless router may operate in accordance with one or more industry standards (e.g., WIFI, Bluetooth) to transmit and receive local area signals 126. A distribution server 106 distributes slices 11 (e.g., via a wireline or wireless connection) to one or more of the wireless transceiver 112, the low tier user device 114, and the user device 12. Such a wireless transceiver 112 converts slices into local area signals 126 for transmission to one or more wireless devices. Such a wireless transceiver may operate in accordance with one or more industry standards (e.g., WIFI, Bluetooth) to transmit and receive local area signals.

User device 12 and low tier user device 114 include wireline communication capability (e.g., a wireline interface). Wireless user device 110 includes a wireless transceiver to communicate wide area signals 124 and/or local area signals 126 with one or more of another wireless user device 110, the base station 108, the wireless router 104, and the wireless transceiver 112. Such a user device, low tier user device, and wireless user device communicate with the computing system via one or more of the base station, the wireless router, the wireless transceiver, the distribution server, and the network 24 to receive public pillar slices for at least temporary storage, request target content, and receive private pillar slices for non-temporary storage.

User device 12, low tier user device 114, and wireless user device 110 include DS processing which functions include one or more of temporarily storing public pillar slices, deleting temporarily stored public pillar slices when such slices are not required, storing private pillar slices, dispersed storage error decoding slices into target content, dispersed storage error encoding target content into slices, transcoding slices that were encoded with a first set of dispersal parameters into slices encoded with a second set of dispersal parameters, determining user content preferences, identifying target content, facilitating requesting target content, facilitating sharing target content, or consuming target content (e.g., playing a movie, playing a music file, etc.)

FIG. 9A is a flowchart illustrating an example of facilitating partial content downloading (pre-positioning). The method begins with a step 128 where a processing module (e.g., of a dispersed storage (DS) processing unit, a user device) identifies target content for a user device. Such a determination may be based on one or more of a user content preference, a new content listing message, user desired content, a user content selection, user content selection history, a predictive algorithm, a message, a match to a demographic fit, or content already sent. For example, the processing module identifies the target content when the target content includes music from an artist that matches an artist entry of the user content preference.

The method continues at step 130 where the processing module identifies public pillars corresponding to the target content for partial download. Such an identification may be based on one or more of the target content, error coding parameters (e.g., a pillar width, a decode threshold, a write threshold, a read threshold), an amount of data per pillar, a security requirement, a performance requirement, predetermination, a lookup, a pillar assignment for the user device, or a query. For example, the processing module identifies pillars 1-9 as the public pillars corresponding to the target content when a decode threshold is 10 and the security requirement indicates a withholding pattern to withhold one pillar. Such a withholding pattern may indicate to withhold one or more pillars of a decode threshold number of pillars.

The method continues at step 132 where the processing module determines a partial downloading schedule for sending public pillar encoded data slices corresponding to the public pillars. Such a schedule may include a start time, an end time, how much of the target content to partially download, a minimum download rate, an average download rate, or a maximum download rate. Such a determination may be based on one or more of a network loading indicator, historical network loading information, the target content, the size of the target content, a size of encoded data slices associated with the public pillars, user device availability, a user device type indicator (e.g., wireless and/or wireline), or a security requirement. For example, the processing module determines to start the download to a wireless user device, with a maximum download rate of 3 kilobits per second, at 3 AM and complete the download by 5 AM when the historical network loading information indicates that a wireless network associated with the network typically has more available capacity in this time frame and the wireless user device is available.

The method continues at step 134 where the processing module facilitates partial downloading of the target content by facilitating sending of the public pillar encoded data slices to the user device. Such facilitation includes at least one of retrieving of the public pillar encoded data slices when the processing module is associated with the user device and requesting sending of the public pillar encoded data slices when the processing module is associated with a DS processing unit.

In an example of operation, in step 128, a wireless user device 110 operably coupled to base station 108 determines a user content preference and identifies target content associated with the user content preference. In step 130, wireless user device 110 identifies public pillars corresponding to the target content for a partial download. In step 132, wireless user device 110 determines a partial downloading schedule (e.g., sending slices on off hours such that base station effectiveness is not compromised) for retrieving public pillar encoded data slices corresponding to the public pillars. In step 134, wireless user device 110 facilitates partial downloading of the target content by facilitating sending of the public pillar encoded data slices to the wireless user device 110 via the wireless controller 102 and base station 108 utilizing the wide-area signals 124. For example, the wireless user device sends a slice retrieval request to the DSN memory 22, wherein the request includes a slice name associated with a public pillar encoded data slice. Alternatively, or in addition to, the DS processing unit 16, user device 12 or low tier user device 114, determines the user content preference, identifies the target content, identifies the public pillars, determines the partial downloading schedule, and facilitates partial downloading of the target content.

In the example continued, the wireless user device receives the public pillar encoded slices, via the wide area signals, of the target content and stores the slices in a temporary slice memory 118 of the wireless user device. The wireless user device determines whether the target content is desired. For example, the wireless user device receives a user input that selects the target content to indicate that the target content is desired target content. When the target content is desired, the wireless user device identifies one or more required private pillars of the desired target content and requests encoded data slices (e.g., from the DSN memory 22) corresponding to the one or more required private pillars, receives the private pillar encoded data slices via the wide area signals, stores the private pillar encoded data slices in non-temporary slice memory 120, and moves the public pillar encoded data slices from the temporary slice memory 118 to a non-temporary slice memory 120 of the wireless user device 110.

In another example of operation, a wireless user device 110 operably coupled to the wireless router communicates with the DSN memory 22 via the wireless router utilizing the local area signals 126. The wireless user device may forward at least some of the public pillar encoded data slices to another wireless user device operably coupled to the wireless user device utilizing local area signals. In yet another example of operation, the low tier user device 114 communicates with the DSN memory 22 via the distribution server utilizing a wireline connection and facilitates storage of public pillar encoded data slices and private pillar encoded data slices in a slice memory of the distribution server. As such, the low tier user device accesses the slice memory of the distribution server to consume slices as target content.

As yet another example of operation, the DS processing unit 16 selects a plurality of network edge units for staging public pillar encoded data slices. Such a plurality of network edge units includes one or more of the wireless controller 102, the wireless router 104, the distribution server 106, a user device 12, and a wireless user device 110. The DS processing unit 16 identifies target content for partial download to the plurality of network edge units. The DS processing unit 16 identifies public pillars corresponding to the target content for partial download and determines a partial downloading schedule for sending public pillar encoded data slices to each network edge unit of the plurality of network edge units. The DS processing unit 16 facilitates partial downloading of the target content by facilitating sending of the public pillar encoded data slices to each network edge unit of the plurality of network edge units.

In a continuation of the example, at least one of a user device 12 and a wireless user device 110 identify target content and identify public pillars corresponding to the target content. The at least one of the user device and the wireless user device requests a download of the public pillar encoded data slices from at least one of the plurality of network edge units. The at least one of the user device and wireless user device receives the public pillar encoded data slices of the target content and stores the public pillar encoded data slices in a temporary slice memory 118 associated with the at least one of the user device and the wireless user device. The at least one of the user device and the wireless user device downloads corresponding private pillar encoded data slices from at least one of the DSN memory 22 and one of the plurality of network edge units and stores the private pillar encoded data slices in a non-temporary slice memory 120 associated with the at least one of the user device and the wireless user device. The at least one of the user device and the wireless user device moves the public pillar encoded data slices from the temporary slice memory 118 to the non-temporary slice memory 120. The method of operation of the computing system is described in greater detail with reference to FIGS. 9A and 9B.

FIG. 9B is a flowchart illustrating an example of staging content for downloading (pre-positioning). In particular, a method is presented for use in conjunction with one or more functions and features described in conjunction with FIGS. 1-2, 3-9A, and also FIG. 9B.

The method begins with step 136, where processing module (e.g., a dispersed storage (DS) processing unit) selects a plurality of network edge units for staging public pillar encoded data slices. Such a selection may be based on one or more of a list of units, a unit request, a user device operably coupled to the unit, a geographic area associated with a unit, a content preference of a user device, a previous partial download list, a new content listing message, a desired content indicator of a user device, or a content selection history of a user device. For example, processing module selects a network edge unit that is operably coupled to a user device that may require target content downloading.

The method continues with step 138, where the processing module identifies target content for partial download to the plurality of network edge units. Such identifying may be based on one or more of a unit request, a user device operably coupled to the unit, a content preference of a user device, a previous partial download list, a new content listing message, a desired content indicator of a user device, or a content selection history of a user device. The method continues with step 130 of FIG. 9A, where the processing module identifies public pillars corresponding to the target content for partial download.

The method continues at step 142, where the processing module determines a partial downloading schedule for sending public pillar encoded data slices, corresponding to the public pillars, to each network edge unit of the plurality of network edge units. Such a schedule may include a start time, an end time, how much of the target content to partially download, a minimum download rate, an average download rate, or a maximum download rate. Such a determination may be based on one or more of a location of the network edge unit, an availability indicator of the network edge unit, a network loading indicator associated with the network edge unit, and available network bandwidth associated with the network edge unit, a location of a user device, an availability indicator of a user device associated with the network edge unit, a network loading indicator, historical network loading information, the target content, the size of the target content, a size of encoded data slices associated with the public pillars, a user device type indicator (e.g., wireless and/or wireline), or a security requirement. For example, the processing module determines to start the download to a network edge unit, with a maximum download rate of 5 Mb per second, at 11:01 PM and complete the download by 11:15 PM when the historical network loading information indicates that the network edge unit typically has more available network bandwidth in this time frame.

The method continues at step 144, where the processing module facilitates partial downloading of the target content by facilitating sending of the public pillar encoded data slices to each network edge unit of the plurality of network edge units. Such facilitation includes at least one of retrieving of the public pillar encoded data slices when the processing module is associated with the network edge unit and requesting sending of the public pillar encoded data slices when the processing module is associated with a DS processing unit.

The method described above in conjunction with the processing module can alternatively be performed by other modules of the dispersed storage network or by other computing devices. In addition, at least one memory section (e.g., a non-transitory computer readable storage medium) that stores operational instructions can, when executed by one or more processing modules of one or more computing devices of the dispersed storage network (DSN), cause the one or more computing devices to perform any or all of the method steps described above.

It is noted that terminologies as may be used herein such as bit stream, stream, signal sequence, etc. (or their equivalents) have been used interchangeably to describe digital information whose content corresponds to any of a number of desired types (e.g., data, video, speech, audio, etc. any of which may generally be referred to as ‘data’).

As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “configured to”, “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for an example of indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “configured to”, “operable to”, “coupled to”, or “operably coupled to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform, when activated, one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item.

As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2, a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1. As may be used herein, the term “compares unfavorably”, indicates that a comparison between two or more items, signals, etc., fails to provide the desired relationship.

As may also be used herein, the terms “processing module”, “processing circuit”, “processor”, and/or “processing unit” may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module, module, processing circuit, and/or processing unit may be, or further include, memory and/or an integrated memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of another processing module, module, processing circuit, and/or processing unit. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that if the processing module, module, processing circuit, and/or processing unit implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Still further note that, the memory element may store, and the processing module, module, processing circuit, and/or processing unit executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the Figures. Such a memory device or memory element can be included in an article of manufacture.

One or more embodiments have been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claims. Further, the boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality.

To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claims. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof.

In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.

The one or more embodiments are used herein to illustrate one or more aspects, one or more features, one or more concepts, and/or one or more examples. A physical embodiment of an apparatus, an article of manufacture, a machine, and/or of a process may include one or more of the aspects, features, concepts, examples, etc. described with reference to one or more of the embodiments discussed herein. Further, from figure to figure, the embodiments may incorporate the same or similarly named functions, steps, modules, etc. that may use the same or different reference numbers and, as such, the functions, steps, modules, etc. may be the same or similar functions, steps, modules, etc. or different ones.

Unless specifically stated to the contra, signals to, from, and/or between elements in a figure of any of the figures presented herein may be analog or digital, continuous time or discrete time, and single-ended or differential. For instance, if a signal path is shown as a single-ended path, it also represents a differential signal path. Similarly, if a signal path is shown as a differential path, it also represents a single-ended signal path. While one or more particular architectures are described herein, other architectures can likewise be implemented that use one or more data buses not expressly shown, direct connectivity between elements, and/or indirect coupling between other elements as recognized by one of average skill in the art.

The term “module” is used in the description of one or more of the embodiments. A module implements one or more functions via a device such as a processor or other processing device or other hardware that may include or operate in association with a memory that stores operational instructions. A module may operate independently and/or in conjunction with software and/or firmware. As also used herein, a module may contain one or more sub-modules, each of which may be one or more modules.

As may further be used herein, a computer readable memory includes one or more memory elements. A memory element may be a separate memory device, multiple memory devices, or a set of memory locations within a memory device. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. The memory device may be in a form a solid-state memory, a hard drive memory, cloud memory, thumb drive, server memory, computing device memory, and/or other physical medium for storing digital information.

While particular combinations of various functions and features of the one or more embodiments have been expressly described herein, other combinations of these features and functions are likewise possible. The present disclosure is not limited by the particular examples disclosed herein and expressly incorporates these other combinations. 

What is claimed is:
 1. A method for execution by one or more processing modules of one or more computing devices of a storage network, the method comprises: selecting a plurality of network edge units for staging public pillar encoded data slices, wherein the networking edge units are operably coupled to a user device that requires target content downloading; identifying the target content for partial download to the plurality of network edge units; disperse error encoding the target content to generate a pillar width set of encoded data slices, wherein the pillar width set includes the public pillar encoded data slices and private pillar encoded data slices; identifying the public pillars encoded data slices corresponding to the target content for partial download; determining a partial downloading schedule for sending public pillar encoded data slices to each network edge unit of the plurality of network edge units; and facilitating partial downloading of the target content by facilitating sending of the public pillar encoded data slices to each network edge unit of the plurality of network edge units, wherein the facilitating partial downloading of the target content includes at least one of: retrieving of the public pillar encoded data slices when a processing module is associated with the network edge units or request sending of the public pillar encoded data slices when the processing module is associated with a distributed storage (DS) processing unit.
 2. The method of claim 1, wherein the selecting a plurality of network edge units for staging public pillar encoded data slices is based on one or more of: a list of units, a unit request, a user device operably coupled to a unit, a geographic area associated with a unit, a content preference of a user device, a previous partial download list, a new content listing message, a desired content indicator of a user device, or a content selection history of a user device.
 3. The method of claim 1, wherein the identifying target content for partial download is based on one or more of: a unit request, a user device operably coupled to a unit, a content preference of a user device, a previous partial download list, a new content listing message, a desired content indicator of a user device, or a content selection history of a user device.
 4. The method of claim 1, wherein the determining a partial downloading schedule is based on one or more of: a location of a network edge unit, an availability indicator of the network edge unit, a network loading indicator associated with the network edge unit, available network bandwidth associated with the network edge unit, a location of a user device, an availability indicator of a user device associated with the network edge unit, a network loading indicator, historical network loading information, the target content, a size of the target content, a size of encoded data slices associated with the public pillars, a user device type indicator, or a security requirement.
 5. The method of claim 1, wherein the partial downloading schedule includes one or more of: a start time, an end time, how much of the target content to partially download, a minimum download rate, an average download rate, or a maximum download rate.
 6. The method of claim 1, wherein the identifying public pillars corresponding to the target content for partial download is based on: target content, error coding parameters, an amount of data per pillar, a security requirement, a performance requirement, a predetermination, a lookup, or a query.
 7. A computing device of a group of computing devices of a storage network, the computing device comprises: an interface; a local memory; and a processing module operably coupled to the interface and the local memory, wherein the processing module is configured to: select a plurality of network edge units for staging public pillar encoded data slices; identify target content for partial download to the plurality of network edge units; identify public pillars corresponding to the target content for partial download, wherein the target content is encoded as a pillar width set of encoded data slices including the public pillar encoded data slices and private pillar encoded data slices; determine a partial downloading schedule for sending the public pillar encoded data slices to each network edge unit of the plurality of network edge units; and facilitate partial downloading of the target content by facilitating sending of the public pillar encoded data slices to each network edge unit of the plurality of network edge units.
 8. The computing device of claim 7, wherein the select a plurality of network edge units for staging public pillar encoded data slices is based on one or more of: a list of units, a unit request, a user device operably coupled to a unit, a geographic area associated with a unit, a content preference of a user device, a previous partial download list, a new content listing message, a desired content indicator of a user device, or a content selection history of a user device.
 9. The computing device of claim 7, wherein the select a plurality of network edge units for staging public pillar encoded data slices includes selecting a network edge unit that is operably coupled to a user device that requires target content downloading.
 10. The computing device of claim 7, wherein the identify target content for partial download is based on one or more of: a unit request, a user device operably coupled to a unit, a content preference of a user device, a previous partial download list, a new content listing message, a desired content indicator of a user device, or a content selection history of a user device.
 11. The computing device of claim 7, wherein the determine a partial downloading schedule is based on one or more of: a location of a network edge unit, an availability indicator of the network edge unit, a network loading indicator associated with the network edge unit, available network bandwidth associated with the network edge unit, a location of a user device, an availability indicator of a user device associated with the network edge unit, a network loading indicator, historical network loading information, the target content, a size of the target content, a size of encoded data slices associated with the public pillars, a user device type indicator, or a security requirement.
 12. The computing device of claim 7, wherein the partial downloading schedule includes one or more of: a start time, an end time, how much of the target content to partially download, a minimum download rate, an average download rate, or a maximum download rate.
 13. The computing device of claim 7, wherein the facilitate partial downloading of the target content includes at least one of: retrieving of the public pillar encoded data slices when the processing module is associated with the network edge units or requesting sending of the public pillar encoded data slices when the processing module is associated with a DS processing unit.
 14. A system including a storage network, the system comprises: an interface; a local memory; and a processing module operably coupled to the interface and the local memory, wherein the processing module is configured to: select a plurality of network edge units for staging public pillar encoded data slices; identify target content for partial download to the plurality of network edge units; identify public pillars corresponding to the target content for partial download, wherein the target content is encoded as a pillar width set of encoded data slices including the public pillar encoded data slices and private pillar encoded data slices; determine a partial downloading schedule for sending the public pillar encoded data slices to each network edge unit of the plurality of network edge units; and facilitate partial downloading of the target content by facilitating sending of the public pillar encoded data slices to each network edge unit of the plurality of network edge units.
 15. The system of claim 14, wherein the select a plurality of network edge units for staging public pillar encoded data slices is based on one or more of: a list of units, a unit request, a user device operably coupled to a unit, a geographic area associated with a unit, a content preference of a user device, a previous partial download list, a new content listing message, a desired content indicator of a user device, or a content selection history of a user device.
 16. The system of claim 14, wherein the select a plurality of network edge units for staging public pillar encoded data slices includes selecting a network edge unit that is operably coupled to a user device that may require target content downloading.
 17. The system of claim 14, wherein the identify target content for partial download is based on one or more of: a unit request, a user device operably coupled to a unit, a content preference of a user device, a previous partial download list, a new content listing message, a desired content indicator of a user device, or a content selection history of a user device.
 18. The system of claim 14, wherein the facilitate partial downloading of the target content includes at least one of: retrieving of the public pillar encoded data slices when the processing module is associated with the network edge units or requesting sending of the public pillar encoded data slices when the processing module is associated with a distributed storage (DS) processing unit. 